majit: Defer Dynasm bridge constant conversion to diagnostic path - #1299
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 2 reviews per rolling hour; 1 remains after this review. WalkthroughThe change reorders trace-diagnostic evaluation in ChangesCompile bridge diagnostic ordering
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: 🟡 Moderate · up to The Dynasm backend change is not merge-ready until the required checks run successfully or their omission is explicitly accepted; the current environment lacks the Rust toolchain needed to execute them. Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🤖 Codex parity reviewStatic analysis of this diff vs the local RPython/PyPy sources (commit 4ba378b). Files in the reviewed diff1. Regressions to PyPy parity introduced by this patchNone. 2. Other mismatches introduced by this patchNone. 3. Pre-existing mismatches (already present before this patch)None. 4. Structural adaptationsNone. |
youknowone
left a comment
There was a problem hiding this comment.
Thank you so much! and welcome to Pyre project!
Summary
Move the raw constant map conversion into the
PYRE_TRACE_OPS_DIAGbranch, avoiding diagnostic-only allocation and iteration during normal bridge compilation.compile_loophas similarconst_poolcollection logic, but I left it duplicated rather than extracting a helper that isn't needed yet.pyre/majit/majit-backend-dynasm/src/runner.rs
Lines 2394 to 2397 in 21ce530
Self-review
Assisted-bySummary by CodeRabbit